-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fallback solution: Parse "artist-title" with a single dash from file name #3082
Conversation
What happens if I have a track named "Some Track (Some Artist Re-Mix).mp3"? I think we should not parse artist-title with a single dash. No magic is far better than broken magic. The person could just tag the files correctly or use |
Now we have a complain that "artist-title" is not supported which was the 2.2 state. We had never complains about false positives. Importing "Some Track (Some Artist Re-Mix).mp3" as Artist: "Some Track (Some Artist Re" Track: "Mix" is probably also not too bad, because you need to adjust the naming anyway. What do you think? |
Why do you need to adjust the naming anyway? I think that broken parsing is way worse than no parsing at all (even in the artist-title case). |
Because else I have Title and artist in the title field. This is finally a personal preference we can't solve in a discussion. I always use spaces, so I don't really mind. The valid argument to me here is that this was reported as a regression and the regression is fixed with this PR. |
No, you only have the title in the title field and no artist at all (as there is no artist is in the filename).
How you name your files is indeed personal preference. Mixxx making wrong assumptions about the file name and applying broken magic where it shouldn't is not personal preference.
This is an artificial example because I always tag my files, but AFAIK the default naming scheme for iTunes looks like this: I think it's reasonable to assume
It's a regression in so far as previous behavior has changed. The original behavior was wrong and I'd consider it a bug. I think it's reasonable to ask the reporter to either fix their file names/tags or live without the magic artist/title parsing. |
The point is, that we have no evidence for this but for the opposite. |
...and those discussions show once again why adding this "feature" in the first place was a bad idea. I always wanted to delete the code, even if users might complain. Most of them are not even aware that there are better ways for managing metdata. Mixxx prevents them from realizing this. |
As requested and suggested on Discourse: https://mixxx.discourse.group/t/metadata-from-filename-not-creating-artist-title/19901
??? |
I vote for merge, the work is done and one user will be happy. |
I'm not happy about this. If you really think this is needed instead of users just fixing their tags or naming scheme (which can easily be done with a bulk rename, e. g. using
Even with these additional rules, I doubt that it is worth it to introduce this complexity (which might still fail to detect undesired splitting) when the user could just fix the naming of the files with minimal effort. But if you deem it necessary I won't vote against the merge then. |
My preferred solution would be to just use the file name excluding the last suffix as the title and get rid of this poor parser. |
As requested and suggested on Discourse:
https://mixxx.discourse.group/t/metadata-from-filename-not-creating-artist-title/19901
Could be considered a regression from 2.2. This simple fallback solution should not cause any unintended side-effects.